<p>With the ubiquity of media coverage around “AI everything” and companies racing to add shiny new “AI-driven” features, having a working understanding of the fundamental technologies driving the hype will help you find ways to leverage the good parts and …</p>
<p>With the version 1.0 release of</p><p>react-router</p><p>, the named</p><p>Route</p><p>feature was dropped. In</p><p>earlier versions</p><p>, you were able to define each</p><p>Route</p><p>with a</p><p>name</p><p>parameter:</p><p><</p><p>Route</p><p>path</p><p>=</p><p>"/account/billing"</p><p>name</p><p>=</p><p>"account-billing"</p><p>/></p><p>and link …</p>
<p>[with apologies to Mr. Orwell]</p><p>I’ve noticed a subtle shift in how we approach building up new sites over the last couple of years. Our approach to site construction used to favor collecting open source apps and gluing them together …</p>
<p>Our team functions in different capacities for each business engagement, but we typically have a project or few where we’re exclusively building a large site for a client. In those scenarios we tend to use a loosely defined two-week development …</p>
<p>We’ve made it a general rule to move away from relying on fixtures in our projects. The main reasons are:</p><p>Fixtures are fragile. They often break when the schema changes or even worse they appear to work but introduce subtle …</p>
<p>It is often handy to disable (either temporarily or permanently) South migrations for an app. “Disable” in this context means preventing an app’s migrations from being executed so that the app is managed via</p><p>syncdb</p><p>while in this state. A …</p>
<p>Why?</p><p>A common question from South users is how to reset the migrations back to an initial state. The reasons for doing this are often related to the number of migrations growing steadily over the life of the project. You’ve …</p>
